refactor(util): change traversal strategy in root_pattern #3552
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the previous implementation, there was a priority order in defining the root_file.
I have modified it to give priority to the configuration file that is closer to the current directory.
For example
In the case where it runs from monorepo/packages/something,
if both
monorepo/packages/something/eslint.config.js
andmonorepo/.eslintrc
exist, the execution root is currently set tomonorepo
.However, I believe that the closer file
monorepo/packages/something/eslint.config.js
should be prioritized, and the execution root should bemonorepo/packages/something
instead ofmonorepo
.